Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Count reverse offset from the back of the geometry, not the front. #5315

Merged
merged 4 commits into from
Dec 16, 2018

Conversation

danpat
Copy link
Member

@danpat danpat commented Dec 15, 2018

Issue

Fixes a problem with distance calculations in table responses (reported in #5306).

The reverse offset value in the PhantomNodes was being incorrectly calculated. When this value was used, and the matrix covered only a small distance, it was possible for the incorrect offset to outweigh the distances added to it, and it would end up negative..

Tasklist

Requirements / Relations

Link any requirements here. Other pull requests this PR is based on?

…d fix some tests that were incorrect due to the bug.
…atrices should've been symmetrical (a->o == o->a for these cases)
@danpat danpat merged commit 1eab7b4 into master Dec 16, 2018
datendelphin added a commit to fossgis-routing-server/osrm-backend that referenced this pull request Nov 19, 2020
  - Changes from 5.20.0
    - Features:
      - ADDED: all waypoints in responses now contain a distance property between the original coordinate and the snapped location. [Project-OSRM#5255](Project-OSRM#5255)
      - ADDED: if `fallback_speed` is used, a new structure `fallback_speed_cells` will describe which cells contain estimated values [Project-OSRM#5259](Project-OSRM#5259)
      - REMOVED: we no longer publish Node 4 or 6 binary modules (they are still buildable from source) [Project-OSRM#5314](Project-OSRM#5314)
    - Table:
      - ADDED: new parameter `scale_factor` which will scale the cell `duration` values by this factor. [Project-OSRM#5298](Project-OSRM#5298)
      - FIXED: only trigger `scale_factor` code to scan matrix when necessary. [Project-OSRM#5303](Project-OSRM#5303)
      - FIXED: fix bug in reverse offset calculation that sometimes lead to negative (and other incorrect) values in distance table results [Project-OSRM#5315](Project-OSRM#5315)
    - Docker:
      - FIXED: use consistent boost version between build and runtime [Project-OSRM#5311](Project-OSRM#5311)
      - FIXED: don't override default permissions on /opt [Project-OSRM#5311](Project-OSRM#5311)
    - Matching:
      - CHANGED: matching will now consider edges marked with is_startpoint=false, allowing matching over ferries and other previously non-matchable edge types. [Project-OSRM#5297](Project-OSRM#5297)
    - Profile:
      - ADDED: Parse `source:maxspeed` and `maxspeed:type` tags to apply maxspeeds and add belgian flanders rural speed limit. [Project-OSRM#5217](Project-OSRM#5217)
      - CHANGED: Refactor maxspeed parsing to use common library. [Project-OSRM#5144](Project-OSRM#5144)
@DennisOSRM DennisOSRM deleted the danpat_fix_negative_table_distances branch November 6, 2022 14:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant